-
Notifications
You must be signed in to change notification settings - Fork 6
add oci pull to images #175
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
|
@majst01 okay, so this is what I came up with. Can you do a review, pls? Besides, I'm wondering if it's suitable to retrieve the oci credentials from env vars. Can you help me out here? |
The OCI creadentials should be passed as optional fields from the pixiecore to the metal-hammer: https://github.com/metal-stack/metal-hammer/blob/master/cmd/pixie-client.go#L14 Ideally a slice of registryconfig which contains the registry url, the username and the password should come from pixiecore. |
|
@majst01 does this work? https://github.com/metal-stack/metal-hammer/pull/175/files#diff-cfcd5a78ad9476ee24d7680dd023e71136f329c771d76ae6837ba68320b6379cR37 what does |
It contains the full URL as configured in the image |
0bfe689 to
7052ccb
Compare
machine.Allocation.Image.URL can be used without auth
since it's not supported by name.ParseReference
…nd default to image
ad2bb15 to
2506148
Compare
2a95918 to
b244121
Compare
57274af to
ffebda3
Compare
since they're considered integration tests and can't be run inside a docker container due to testcontainers-go
Description
References
TODO